-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Team Compass to include Partnerships Charter and new org structure #759
Conversation
Refactoring to align with new organizational structure.
Update index.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've pushed a commit that does a bit more restructuring so that we clarify that "Community guidance", its roles, its operations, etc are underneath "Partnerships". It also moves Product under an org-wide area rather than a functional area. This is mostly just moving stuff around and nesting it inside of Partnerships, not changing any content. There are also a couple bugs in the docs that I fixed along the way.
For deciding on this PR, I think it's best to still just focus on the content nested underneath the partnerships/
.
I'm happy to merge this in, since it's a better reflection of our current / aspirational structure. I think we'll need to revisit some of these areas as we understand 2i2c's org structure better, but this is a good start.
@@ -13,5 +13,6 @@ google-workspace | |||
github | |||
airtable | |||
authentication | |||
passwords |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fixing a bug where we forgot to add the passwords page in the toctree for this section
@@ -48,7 +48,7 @@ operations/index | |||
people/index | |||
open-source/index | |||
finance/index | |||
communication/index |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving "communication" pages into the Partnerships area, because this is effectively marketing and community engagement.
|
||
```{toctree} | ||
overview.md | ||
structure.md | ||
workflow.md | ||
communication.md | ||
../communication/index | ||
community_success/freshdesk.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Over time we might want to nest more pages under community_success if more content is added there, so I just created a sub-folder for now w/ the freshdesk tips page in it. This is under the assumption that support mechanisms will fall under Partnerships
- **Training**: Help communities understand how to use our products and services to achieve value. | ||
- **Community satisfaction**: Understand the ongoing satisfaction that communities have with the service and identify ways to improve their experience. | ||
- **Account management**: Establish and sustain relationships with partner organizations to ensure they are successful. | ||
- **Grant management**: Ensure that the goals and deliverables of our grants are understood and met. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels like "Project management" to me. Is that your intention? E.g., if we hired a project manager would you imagine them reporting somewhere in the Partnerships chain?
We can have it here for now and revisit later if it becomes relevant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These headings were introduced to describe major functional areas or work streams under Partnerships. I do not believe Partnerships is the natural umbrella for all "Project Manager" roles within 2i2c. Development projects mostly involving engineering (e.g. SOLyR?) should not be managed by a role in Partnerships.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're aligned on this - though there's an interesting question about who is the ultimate "owner" of a grant and its deliverables in 2i2c, given that most grants are cross-functional. I think this is a role that we're missing and as a result I am the de-facto owner of all grants which is not sustainable.
# Community success manager | ||
|
||
```{warning} To add | ||
To add here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got confirmation from @colliand that he is okay to merge this one as-is and start iterating from there. So I will merge this, and ask that folks update the content and descriptions as they come into focus. Thanks all! |
This PR contains text changes in the way Partnerships is described. These changes mostly flow from the Partnerships Plan g-doc.
Related PRs